home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c,comp.lang.c++
- Subject: Re: Borland should be ashamed. My experience with BC5.0.
- Date: 19 Apr 1996 10:38:52 -0700
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4l8j3cINNfbr@keats.ugrad.cs.ubc.ca>
- References: <4l6d1b$219@linet06.li.net>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4l6d1b$219@linet06.li.net>, Bob Silvern <bsilvern@li.net> wrote:
- >The problem occurs with all projects on my system. For example,
- >windows/examples/cmdlg/cmdlg.ide.
- >The steps to demonstrate problems 1 and 2 previously described are:
- > 1) Open an editor window containing cmdlg.c.
- > 2) Maximize the window and place the cursor at the end of a line of text.
- >Note the text left of the cursor because it will get deleted later.
- > 3) View, Globals.
- > 4) Place the cursor in the Search box. (Note that alt-h doesn't put the
- >cursor there as implied by the underlined h in "Search". This is another bug
- >which I neglected to mention.)
- > 5) Type "w".
- > 6) 7 types and 1 function are displayed. The 1 function is "int
- >WinMain(HINSTANCE__ *, HINSTANCE__ *,signed char *,int)". So far, so good.
- > 7) Now type "i" so that the Search box reads "wi". All 8 items are erased
- >from the display, including WinMain, which of course should still be visible.
- >This is problem #1.
- > 8) Now hit the backspace key a few times. The characters in the search box
- >are not deleted. Now look at the editor window. The backspace key was
- >deleting the characters in the editor window, not the Search box. This is
- >problem #2. For 3 days I was unjustly accusing my cat of walking on the
- >keyboard as characters seemed to randomly disappear. She has vowed (meowed)
- >never to buy another Borland product again.
-
- There is your problem: in going to a new version of the compiler, you are
- forced to upgrade your editing environment.
-
- You wouldn't be suffering from such B.S. if you used your favorite editor.
-
- Do you actually have an bugs to report about the *compiler*?
-
- >Start from the maximized message window, make the active line a message about
- >foo.c. If you switch to an editor window of foo.c via the window menu or
- >Cntl-F6, you get a maximized editor window with the other windows on top of it.
- >Clicking cursor anywhere in another window maximizes that window.
-
- Cry me a river...
-
- >I have verifed the previously reported problem with the following code:
- >
- >int foo(int i) {
- > int a[4];
- >
- > a[0] = i;
- > a[1] = i;
- > a[2] = i;
- > a[3] = i;
- > a[0] *= 2;
- > a[1] *= 2;
- > a[2] *= 2;
- > a[3] *= 2;
- > return a[3];
- >}
- >
- >int PASCAL WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR
- >lpszCmdLine, int cmdShow) {
- > int k;
- > k = foo(1040);
- >}
- >
- >Steps to create the problem are:
- > 1) Run to line "a[1] = i;" in foo.
- > 2) Watch a, i.
- > 3) Inspect i;
- > 4) In inspect window, change value of i to 33;
- > 5) Single step to line a[0] *= 2;
- > 6) Watch window and inspect window show i =1040 again.
- >
- >Note that a[1], a[2], and a[3] are assigned the proper value of 33, but as soon
- >as i is no longer used it is reported incorrectly.
-
- Maybe the use of i is optimized into a register! Did you turn off
- optimization before you compiled that?
-
- Not that I'm defending Borland---I couldn't care less. But maybe you are wrong.
-